Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0993

reference
260-tree-1
name
0993
tree-preservation-order

undefined

260-tpo-1
uprn
address-text
point
POINT (-0.935600 50.858796)
geometry
MULTIPOLYGON (((-0.935558 50.858791,-0.935560 50.858800,-0.935566 50.858807,-0.935575 50.858813,-0.935587 50.858817,-0.935600 50.858819,-0.935613 50.858818,-0.935625 50.858814,-0.935635 50.858808,-0.935641 50.858801,-0.935643 50.858792,-0.935641 50.858784,-0.935635 50.858776,-0.935626 50.858770,-0.935614 50.858766,-0.935601 50.858765,-0.935588 50.858766,-0.935576 50.858770,-0.935566 50.858776,-0.935560 50.858783,-0.935558 50.858791)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL